Add backbrief-kit to plugins - #40
Open
charlesashe wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a reference entry for
backbrief-kit.What it is: an orchestrator plans a goal into units with acceptance criteria and routes each to a specialist agent; a separate verifier reviews each finished artifact in fresh context against those criteria, receiving the artifact and criteria only and never the producing agent's reasoning;
/handoffand/pickupcarry project state across sessions.Manifest:
.claude-plugin/plugin.json, version 2.10.0.Two notes so the entry is accurate rather than flattering:
commands, notagents/skills. The plugin itself provides two slash commands at its root (/backbrief-kit:setup,/backbrief-kit:verify-install). The agents, skills and rules ship inkit-payload/and are installed into the user's project by/setuprather than loaded as plugin-native components, so tagging them would put the entry in filters where a user would find nothing plugin-native.licensefield rather than shortened to something misleading.Repo: https://github.com/charlesashe/backbrief-kit